Wasmtime: build release artifacts with all-arch.
#5657
Conversation
This allows the `wasmtime` binary provided in our release artifacts to cross-compile: `wasmtime compile` can build a `.cwasm` for any platform that Wasmtime supports, not just the host platform. This may be useful in some deployment scenarios. We don't turn on `all-arch` by default because it increases build time and binary size of Wasmtime itself, and other embedders of the `wasmtime` crate won't necessarily want this; hence, we set it only as part of the CI build configuration. Fixes bytecodealliance#5655.
|
Do you know roughly when this will make it into a release? |
|
Our release process is documented here and this'll get released with 6.0.0 on February 20 |
|
@cfallin it looks like this failed on |
|
Ah nevermind looks like it was failing before this too, I'll try to dig in later |
|
I had verified it builds locally, so at least the |
|
Oh @martindevans I forgot about this but you can also test out the artifacts from the |
|
The I didn't test the equivalent binaries on any other platforms though. |
This allows the
wasmtimebinary provided in our release artifacts to cross-compile:wasmtime compilecan build a.cwasmfor any platform that Wasmtime supports, not just the host platform. This may be useful in some deployment scenarios.We don't turn on
all-archby default because it increases build time and binary size of Wasmtime itself, and other embedders of thewasmtimecrate won't necessarily want this; hence, we set it only as part of the CI build configuration.Fixes #5655.